The Cisco router must be configured with only one local account to be used as the account of last resort in the event the authentication server is unavailable.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-216530	CISC-ND-000490	SV-216530r960969_rule		Medium

Description
Authentication for administrative (privileged level) access to the device is required at all times. An account can be created on the device's local database for use when the authentication server is down or connectivity between the device and the authentication server is not operable. This account is referred to as the account of last resort since it is intended to be used as a last resort and when immediate administrative access is absolutely necessary. The account of last resort logon credentials must be stored in a sealed envelope and kept in a safe. The safe must be periodically audited to verify the envelope remains sealed. The signature of the auditor and the date of the audit should be added to the envelope as a record. An alternative to using a sealed envelope in a safe would be credential files, separated by technology, located in a secured location on a file server, with the files only accessible to those administrators authorized to use the accounts of last resort, and access to that location monitored by a central log server. Administrators should secure the credentials and disable the root account (if possible) when not needed for system administration functions.

Description

Authentication for administrative (privileged level) access to the device is required at all times. An account can be created on the device's local database for use when the authentication server is down or connectivity between the device and the authentication server is not operable. This account is referred to as the account of last resort since it is intended to be used as a last resort and when immediate administrative access is absolutely necessary. The account of last resort logon credentials must be stored in a sealed envelope and kept in a safe. The safe must be periodically audited to verify the envelope remains sealed. The signature of the auditor and the date of the audit should be added to the envelope as a record. An alternative to using a sealed envelope in a safe would be credential files, separated by technology, located in a secured location on a file server, with the files only accessible to those administrators authorized to use the accounts of last resort, and access to that location monitored by a central log server. Administrators should secure the credentials and disable the root account (if possible) when not needed for system administration functions.

STIG	Date
Cisco IOS XR Router NDM Security Technical Implementation Guide	2024-06-06

Details

Check Text ( C-17765r288276_chk )
Step 1: Review the Cisco router configuration to verify that a local account for last resort has been configured. username xxxxxxxxxxxx group netadmin secret 5 xxxxxxxxxxxxxxxxxxxx Note: The following groups should not be assigned to this local account: root-system and root-lr. A custom group that provides appropriate tasks can be used. Step 2: Verify that local is defined after radius or tacas+ in the authentication order as shown in the example below. aaa authentication login default group tacacs+ local If the Cisco router is not configured with only one local account to be used as the account of last resort in the event the authentication server is unavailable, this is a finding.

Check Text ( C-17765r288276_chk )

Step 1: Review the Cisco router configuration to verify that a local account for last resort has been configured.

username xxxxxxxxxxxx
group netadmin
secret 5 xxxxxxxxxxxxxxxxxxxx

Note: The following groups should not be assigned to this local account: root-system and root-lr. A custom group that provides appropriate tasks can be used.

Step 2: Verify that local is defined after radius or tacas+ in the authentication order as shown in the example below.

aaa authentication login default group tacacs+ local

If the Cisco router is not configured with only one local account to be used as the account of last resort in the event the authentication server is unavailable, this is a finding.

Fix Text (F-17762r288277_fix)
Step 1: Configure a local account with the necessary privilege level to troubleshoot network outage and restore operations as shown in the following example: RP/0/0/CPU0:R3(config)#username xxxxxxxxx group netadmin RP/0/0/CPU0:R3(config)#username xxxxxxxxx secret xxxxxx Step 2: Configure the authentication order to use the local account if the authentication server is not reachable as shown in the following example: RP/0/0/CPU0:R3(config)#aaa authentication login default group tacacs+ local

Fix Text (F-17762r288277_fix)

Step 1: Configure a local account with the necessary privilege level to troubleshoot network outage and restore operations as shown in the following example:

RP/0/0/CPU0:R3(config)#username xxxxxxxxx group netadmin
RP/0/0/CPU0:R3(config)#username xxxxxxxxx secret xxxxxx

Step 2: Configure the authentication order to use the local account if the authentication server is not reachable as shown in the following example:

RP/0/0/CPU0:R3(config)#aaa authentication login default group tacacs+ local